-
Notifications
You must be signed in to change notification settings - Fork 427
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Add support for error notifications for Snowpipe #595
Conversation
Are you going to implement the |
Sorry, I was still figuring out how everything works here 😅 . I think I covered everything now? Please let me know if I missed anything, I'm new to this codebase. The name |
Could you also add a new acceptance test with setting the |
Also run |
Are acceptance tests run on an actual Snowflake account? If so, this might be problematic since the error notifications feature is currently in private preview and Snowflake staff need to enable it for that particular account before setting Other stuff is all fixed ✅ |
Something else I missed: I had thought that notification integration needed for this feature was already implemented, but that was only for AZURE_STORAGE_QUEUE and these Snowpipe error notifications only work on AWS for now. So I added an AWS_SQS implementation and corresponding unit tests. Notification integrations can also be GCP_PUBSUB, but that's outside the scope of this pull request and I will leave it for somebody using GCP to implement 🙂 |
Exposed AWS_SQS_EXTERNAL_ID for notification integration, I think that's everything now. Let me know if there's anything else I need to do before this can get merged. |
/ok-to-test sha=b7f0b08 |
Run |
Integration tests failure for b7f0b08 |
I'm looking into turning on the error notifications for our test account, but it looks like there are some other errors... |
Docs re-generated and the two failing tests should now be fixed ✅ |
/ok-to-test sha=479f1ee |
Integration tests success for 479f1ee |
Adding support for error notifications for Snowpipe.
This feature is currently in private preview and must be enabled for the specific account before these changes can work. Once the feature is released (not sure when), it should work for everybody.
The setup consists of a new outbound type of notification integrations (only works with AWS SQS for now):
And the new
ERROR_INTEGRATION
parameter for pipes:Test Plan
References